Bobcares

Unable to connect to a Plesk server via FTP in the passive mode

by | Dec 22, 2021

Unable to connect to a Plesk server via FTP in the passive mode? Read on for a simple solution by our in-house experts.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team recently helped a customer connect to a Plesk server via FTP in the passive mode.

Are you unable to connect to a Plesk server via FTP in the passive mode

If you are unable to connect to a Plesk server through FTP in the passive mode, you are in the right place. Our Support Engineers have been receiving queries from customers who get the following error messages due to this specific error:

  • 530 Login incorrect.
    Login failed.

  • ftp: connect: Connection refused
  • Response: 227 Entering Passive Mode (203,0,113,111,250,241).

    Error: Connection timed out after 20 seconds of inactivity
    Error: Failed to retrieve directory listing
  • ftp: connect: Connection timed out
  • 425 Can’t open data connection.
  • An error occurred opening that folder on the FTP server. Make sure you have permission to access that folder. The operation timed out.
  • Connecting data socket to (203.0.113.2) port 39383
    Socket error (Connection timed out) – reconnecting
  • Error listing directory ‘/httpdocs’. Transfer channel can’t be opened. Reason: No connection could be made because the target machine actively refused it. Could not retrieve the directory listing.

According to our Support Techs, this error makes it impossible to get a directory listing via FTP using Secured TLS. In fact, we will be able to find the error messages in the /var/log/secure file:

pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: Permission denied
pam_systemd(proftpd:session): Failed to connect to system bus: Permission denied
pam_listfile(proftpd:auth): Couldn't open /etc/ftpuser

Interestingly, the error is due to the improper configuration of the passive port range which has a default value of 49152-65535.

How to connect to a Plesk server via FTP in the passive mode

      1. First, we have to log in to Plesk.
      2. Then, we will head to FTP Settings under Tools & Settings. Here, we will specify the passive FTP port range. The default value is 49152-65535.
      3. Next, we have to click Apply or OK to save the changes.
 Unable to connect to a Plesk server via FTP in the passive mode

 

 

 

 

 

 

 

We can do this procedure either via the Plesk interface or directly on the server. Our Support Engineers would like to point out that we have to ensure inbound collections are allowed for the passive FTP port range on the firewall.

[Need a solution to another query? We are just a click away.]

Conclusion

In essence, the skilled Support Engineers at Bobcares demonstrated how to connect to a Plesk server via FTP in the passive mode.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF